Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 10, 2025

Updates the requirements on boto3 to permit the latest version.

Commits
  • 7fa6ec7 Merge branch 'release-1.36.16'
  • df382df Bumping version to 1.36.16
  • dab3dfb Add changelog entries from botocore
  • cc56a2a Merge pull request #4417 from RyanFitzSimmonsAK/develop
  • b087948 Merge branch 'release-1.36.15'
  • 2b18684 Merge branch 'release-1.36.15' into develop
  • 2d30ffe Bumping version to 1.36.15
  • f2ad854 Add changelog entries from botocore
  • d0e608d Merge branch 'release-1.36.14'
  • a1a5aee Merge branch 'release-1.36.14' into develop
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Updates the requirements on [boto3](https://github.com/boto/boto3) to permit the latest version.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@0.0.1...1.36.16)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from pcrespov as a code owner February 10, 2025 04:48
@dependabot dependabot bot added the t:maintenance Some planned maintenance work label Feb 10, 2025
@dependabot dependabot bot requested a review from sanderegg February 10, 2025 04:48
@sonarqubecloud
Copy link

@sanderegg
Copy link
Member

@GitHK Please can you have a look at this update? the constraint was added by you

@GitHK
Copy link
Contributor

GitHK commented Feb 10, 2025

This does not make sense. Current version is 1.36.16 but the issue is still there.

@GitHK GitHK closed this Feb 10, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 10, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/pip/boto3-lt-1.37.0 branch February 10, 2025 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t:maintenance Some planned maintenance work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants